Repository navigation
Conversation
jmgasper
force-pushed
the
security/ecs-oidc-deployment
branch
from
November 3, 2026 21:28
092f78a to
f658e81
Compare
jmgasper
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Move ECS application deployment to repository-bound CircleCI OIDC, targeting
devfor dev validation. The suite is fetched by tag v2.0.6 and verified against26aaf607463d4a271c0099854c1731214215a9c5. Build and deploy jobs remain separate; private IAM templates/baselines stay in v6-services-iac.Pass the reviewed environment-specific health checks to the shared deployer. It adds a missing check with the new scanned image, preserves an identical existing check, and refuses to replace a different one. All role, secret-reference, digest/scan, concurrency and health gates remain enforced. This also prepares the same behavior for the later approved production cutover.
Keep this PR in draft. Security prerequisite #112 and a separate frontend release are still required. Encrypted runtime values are staged and match the legacy image, but the attempted runtime-reference rollout and a fresh unchanged legacy task failed ALB health; rollback restored the original healthy task. New references are not active. Resolve that dev runtime issue before the first new application image.
Validation: all 92 shared tests passed in the pinned AWS executor with networking disabled; all 33 updated CircleCI configs and 60 generic dev/prod wrapper cases passed. Dev task preflight passes with v2.0.6 (this is configuration validation, not application/functional acceptance). Installation evidence and production gates: private provisioning record. Deployment principals retain explicit Parameter Store, Secrets Manager, KMS-decryption and role-chaining denies. Production remains approval-gated after dev validation; no production runtime or ECR settings were changed by this update.